User authentication method and device for credentials back-up service to mobile devices

ABSTRACT

Back-up credentials data is stored for a user. A communication channel is established with a mobile device. A cryptogram is received from the mobile device, such that the cryptogram is relayed by the mobile device from an authentication device that interacted with the mobile device. The authentication device is associated with the user. The cryptogram is verified. In response to the verification of the cryptogram, the stored back-up credentials data is made accessible to the mobile device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to co-pendingU.S. patent application Ser. No. 15/334,800, filed on Oct. 26, 2016,entitled “USER AUTHENTICATION METHOD AND DEVICE FOR CREDENTIALS BACK-UPSERVICE TO MOBILE DEVICES”, which is a continuation of U.S. Ser. No.14/636,619, filed on Mar. 3, 2015, entitled “USER AUTHENTICATION METHODAND DEVICE FOR CREDENTIALS BACK-UP SERVICE TO MOBILE DEVICES,” which isincorporated herein by reference in its entirety for all purposes.

BACKGROUND

Payment accounts are in widespread use. At a point of sale, suchaccounts may be used for purchase transactions, and may be accessed bydevices such as magnetic stripe cards, contactless or contact integratedcircuit (IC) cards (also sometimes referred to as “smartcards”), orpayment-enabled mobile devices, such as payment-enabled smartphones. Inthe case of a payment-enabled mobile device, it may emulate acontactless IC payment card by engaging in an exchange of communicationswith a point of sale (POS) terminal. The exchange of communications mayinclude transmission of a payment account indicator—PAN (“primaryaccount number”) or payment token—from the payment-enabled mobile deviceto the POS terminal. The POS terminal may then generate a transactionauthorization request message, including the payment account indicator,and the transaction authorization request message may then be routed(with de-tokenization if necessary) for approval by the payment accountissuer.

According to some proposals, a payment-enabled mobile device may be usedto access a number of different payment accounts. A so-called “walletapp” may run on the mobile device to aid the user in managing andselecting among the payment accounts accessible via the mobile device.In such cases, it may be said that the mobile device serves as a“digital wallet.”

Of course, it is not unusual for consumers to trade-in, or even lose,their mobile devices. In connection with widespread use of digitalwallets based on mobile devices, there may be a need to quickly,securely and easily load relevant payment credentials onto a new device.It would be desirable for such a process that there be very strongauthentication of the user, since otherwise a wrongdoer may possiblyobtain access to all the legitimate user's credentials.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of some embodiments of the present disclosure,and the manner in which the same are accomplished, will become morereadily apparent upon consideration of the following detaileddescription of the disclosure taken in conjunction with the accompanyingdrawings, which illustrate preferred and exemplary embodiments and whichare not necessarily drawn to scale, wherein:

FIG. 1 is a block diagram of a conventional payment system.

FIG. 2 is a block diagram that illustrates a system for providing accessto payment credentials to a mobile device from a credentials back-upservice in accordance with aspects of the present disclosure.

FIG. 3 is a schematic plan view of a user authentication device providedin accordance with aspects of the present disclosure and shown as partof the system of FIG. 2.

FIG. 3A is a block diagram that shows some details of the authenticationdevice of FIG. 3.

FIG. 4 is a block diagram of a payment-enabled mobile device provided inaccordance with aspects of the present disclosure and that may be usedin connection with the system of FIG. 2.

FIG. 5 is a block diagram that illustrates a computer system that may beoperated as part of the system of FIG. 2 and in accordance with aspectsof the present disclosure.

FIGS. 6A and 6B together form a flow chart that illustrates a processthat may be performed in the system of FIG. 2 in accordance with aspectsof the present disclosure.

DETAILED DESCRIPTION

In general, and for the purpose of introducing concepts of embodimentsof the present disclosure, a user of a mobile device may be suppliedwith a separate authentication device that may be used to triggerdownloading of back-up credentials data to the mobile device. Theback-up credentials data may have previously been securely stored in thecomputer of a credentials back-up service. The authentication device maygenerate a cryptogram that is forwarded to the credentials back-upcomputer via the mobile device to authenticate the mobile device to theback-up computer. The credentials may then be downloaded from theback-up computer to the mobile device.

In some embodiments, the generation of the cryptogram may be preceded bya user authentication process conducted via the mobile device and theauthentication device.

In many cases, the user may elect to store the authentication device ina safe place in the user's residence, and may take out and use theauthentication device only on the rather infrequent occasions when theuser replaces his/her mobile device.

With this approach, there is a high degree of assurance that a mobiledevice that requests a download of back-up credentials data is actuallyin the possession of the legitimate user.

FIG. 1 is a block diagram of a conventional payment system 100.

The system 100 includes a conventional payment card/device 102. Withpertinence to the present disclosure, the payment device 102 may be apayment-enabled mobile device that stores credentials for a number ofpayment accounts and runs a wallet app, as well as one or more paymentapps. The system 100 further includes a reader component 104 associatedwith a POS terminal 106. In some known manner (depending on the type ofthe payment device 102) the reader component 104 is capable of readingthe payment account number and other information from the payment device102.

The reader component 104 and the POS terminal 106 may be located at thepremises of a retail store and operated by a sales associate of theretailer for the purpose of processing retail transactions.

A computer 108 operated by an acquirer (acquiring financial institution)is also shown as part of the system 100 in FIG. 1. The acquirer computer108 may operate in a conventional manner to receive an authorizationrequest for the transaction from the POS terminal 106. The acquirercomputer 108 may route the authorization request via a payment network110 to the server computer 112 operated by the issuer of a paymentaccount that is associated with the payment card/device 102. As is alsowell known, the authorization response generated by the payment accountissuer server computer 112 may be routed back to the POS terminal 106via the payment network 110 and the acquirer computer 108.

One well known example of a payment network is referred to as the“Banknet” system, and is operated by MasterCard InternationalIncorporated, which is the assignee hereof.

The payment account issuer server computer 112 may be operated by or onbehalf of a financial institution (“FI”) that issues payment accounts toindividual users. For example, the payment account issuer servercomputer 112 may perform such functions as (a) receiving and respondingto requests for authorization of payment account transactions to becharged to payment accounts issued by the FI; and (b) tracking andstoring transactions and maintaining account records.

The components of the system 100 as depicted in FIG. 1 are only thosethat are needed for processing a single transaction. A typical paymentsystem may process many purchase transactions (including simultaneoustransactions) and may include a considerable number of payment accountissuers and their computers, a considerable number of acquirers andtheir computers, and numerous merchants and their POS terminals andassociated proximity reader components. The system may also include avery large number of payment account holders, who carry payment devicesfor initiating payment transactions by presenting a payment accountnumber to the reader component of a POS terminal.

FIG. 2 is a block diagram that illustrates a system 200 provided inaccordance with aspects of the present disclosure. The system 200facilitates provision of credentials back-up services to users of mobiledevices such as the device 202 shown in FIG. 2. For purposes ofillustration, the mobile device 202 is assumed to be a payment-enabledsmartphone. Details of the mobile device 202 will be described belowwith reference to FIG. 4. With respect to a conventional payment systemsuch as that shown in FIG. 1, the mobile device 202, at leastpotentially, may incorporate the functionality of the payment device 102shown in FIG. 1.

Also shown in FIG. 2 is an authentication device 204. Details of theauthentication device 204 will be described below, partly in conjunctionwith FIGS. 3 and 3A.

Also shown as part of the system 200 is a credentials back-up computer206. In some embodiments, the credentials back-up computer 206 may serveas a central, secure, but remotely accessible, repository of paymentcredentials data for a population of users of mobile devices. Details ofthe credentials back-up computer 206 will be described below inconnection with FIG. 5, and additional functional aspects will bedescribed in connection with FIGS. 6A and 6B.

Reference numeral 208 indicates communication facilities by which themobile device is connected for purposes of data communication with,e.g., the credentials back-up computer 206. The communication facilities208, for example, may include portions of a mobile communicationsnetwork (not separately shown) for which the mobile device 202 is asubscriber device. Moreover, the communication facilities 208 mayinclude portions of the Internet or other data networks (not separatelyshown) so that a data communication channel may be established betweenthe mobile device 202 and the credentials back-up computer 206.

A practical embodiment of the system 200 may include numerous instancesof the mobile device 202 and the authentication device 204, which may beused and/or held for future use by numerous individuals/users (notshown).

FIG. 3 is a schematic plan view of an embodiment of the authenticationdevice 204 shown in FIG. 2. In its hardware aspects, the authenticationdevice 204 may resemble a typical contactless IC (integrated circuit)payment card.

In the embodiment shown in FIG. 3, the authentication device 204 mayinclude a support structure 302 that has an outer surface that defines acard shaped body. The card shaped body may have the same form factor asa conventional payment card and may be similar in construction to apayment card, i.e., formed from one or more layers of plastic (notseparately indicated).

The authentication device 204 further includes an IC 304 and an antenna306, both supported in or on the support structure 302. As seen fromFIG. 3A, the IC 304 may include a processor 320, a memory 322 and acommunications transceiver 324. The communications transceiver 324 maycouple the processor 320 to the antenna 306. Continuing to refer to FIG.3A, the memory 322 may be in communication with the processor 320 andmay store program instructions. The program instructions may control theprocessor 320 to perform functions as described herein. The processor320 may control the communications transceiver 324 so that the processor320 is enabled to receive and transmit data via the transceiver 324 inthe form of short-range data communications.

As shown in FIG. 3, the antenna 306 may comprise several loops along theperiphery of the support structure 302.

The IC 304 may include electrically conductive contact pads 308 and 310,by which the communications transceiver 324 of the IC 304 may beelectrically connected to the antenna 306.

The authentication device 204 (FIG. 3) may be personalized by storage ofuser-specific data in the memory 322 (FIG. 3A) of the IC 304.

In some embodiments, the authentication device 204 may lack many, andperhaps all, of the visible/human readable information and other visiblefeatures commonly present on a typical IC payment card. Thus, theauthentication device 204 may lack any visible payment account number,expiration date, etc. By the same token, the authentication device 204may differ from a typical IC payment card in that the former may notelectronically store any payment account number or substitute therefor.Moreover, the authentication device 204 may entirely lack any datarelated to a particular payment account and thus may not store anypayment account credentials at all. More generally, the authenticationdevice 204 may not store any of the credentials data referred to belowin conjunction with the description of the credentials back-up computer206. In some embodiments, the authentication device 204 may store one ormore application programs and related data as required for it to playits role in a user authentication and mobile device authenticationprocess as described below in connection with FIGS. 6A and 6B. Theauthentication-related information stored in the authentication device204 (i.e., in the IC 304) may include one or more cryptographic keys(e.g., a public key) as is well known in the art, as well as datarequired for the authentication device 204 to verify user authenticationinformation to be provided by the user in connection with the process ofFIGS. 6A and 6B.

It may further be the case that the authentication device 204 lacks anyvisible branding of a payment network or of a payment account issuer. Insome embodiments, the authentication device 204 may include visiblebranding (not shown) of the provider of credentials data back-upservices via the credentials back-up computer 206. It may also bedesirable that the name and residential address of the user of theauthentication device 204 be visibly reproduced on the authenticationdevice 204.

FIG. 4 is a block diagram that illustrates an example embodiment of themobile device 202 shown in FIG. 2 and provided in accordance withaspects of the present disclosure. The mobile device 202 may beconventional in its hardware aspects. For example, the mobile device 202may be a smartphone, and may resemble, in some or all of its hardwareaspects and many of its functions, common commercially availablesmartphones. Alternatively, the mobile device 202 may be a tabletcomputer with mobile telecommunications capabilities. The ensuingdescription of the mobile device 202 is based on the assumption that itis embodied as a smartphone; those who are skilled in the art willreadily understand from the following description how to embody themobile device 202 as a tablet computer or other device apart from asmartphone.

The mobile device 202 may include a conventional housing (indicated bydashed line 402 in FIG. 4) that contains and/or supports the othercomponents of the mobile device 202. The housing 402 may be shaped andsized to be held in a user's hand, and may, for example, exhibit thetype of form factor that is common with the current generation ofsmartphones.

The mobile device 202 further includes conventional control circuitry404, for controlling over-all operation of the mobile device 202. Forexample, the control circuitry 404 may include a conventional processorof the type designed to be the “brains” of a smartphone.

Other components of the mobile device 202, which are in communicationwith and/or controlled by the control circuitry 404, include: (a) one ormore memory or storage devices 406 (e.g., program and working memory,etc.); (b) a conventional SIM (subscriber identification module) card408; (c) a conventional touchscreen 412 which serves as the primaryinput/output device for the mobile device 202, and which thus receivesinput information from the user and displays output information to theuser. As is the case with many models of smartphones, in someembodiments, the mobile device 202 may also include a fewphysically-actuatable switches/controls (not shown), such as anon/off/reset switch, a menu button, a “back” button, a volume controlswitch, etc. It may also be the case that the mobile device 202 includesa conventional digital camera, which is not explicitly shown.

The mobile device 202 also includes conventional receive/transmitcircuitry 416 that is also in communication with and/or controlled bythe control circuitry 404. The receive/transmit circuitry 416 is coupledto an antenna 418 and provides the communication channel(s) by which themobile device 202 communicates via the mobile telephone communicationnetwork (which, e.g., is included in the above-mentioned communicationfacilities 208, FIG. 2).

Continuing to refer to FIG. 4, the receive/transmit circuitry 416 mayoperate both to receive and transmit voice signals, in addition toperforming data communication functions. As is known to those who areskilled in the art, such data communication may be via HTTP (HyperTextTransfer Protocol) or other communication protocol suitable for carryingout data communication over the internet.

The mobile device 202 further includes a conventional microphone 420,coupled to the receive/transmit circuitry 416. Of course, the microphone420 is for receiving voice input from the user. In addition, a speaker422 is included to provide sound output to the user, and is coupled tothe receive/transmit circuitry 416.

The receive/transmit circuitry 416 may operate in a conventional fashionto transmit, via the antenna 418, voice signals generated by themicrophone 420, and to reproduce, via the speaker 422, voice signalsreceived via the antenna 418. The receive/transmit circuitry 416 mayalso handle transmission and reception of text messages and other datacommunications via the antenna 418.

The mobile device 202 may also include payment processor/transceivercircuitry 424 that is partly or wholly dedicated to implementing NFCcommunications functionality of the mobile device 202. The mobile device202 may further include a loop antenna 426, coupled to the NFC circuitry424. In some embodiments, the NFC circuitry 424 may partially overlapwith the control circuitry 404 for the mobile device 202. Moreover, theNFC circuitry 424 is associated with, and may also overlap with, asecure element (SE) 428 that is part of the mobile device 202 and iscontained within the housing 402. The term “secure element” is wellknown to those who are skilled in the art, and typically refers to adevice that may include a small processor and volatile and nonvolatilememory (not separately shown) that are secured from tampering and/orreprogramming by suitable measures. In some embodiments, the secureelement 428 may be provided as part of the SIM card 408. In otherembodiments, the secure element 428 may be constituted by an integratedcircuit card separate from the SIM card 408, but possibly having thesame form factor as the SIM card 408. In some embodiments of the mobiledevice 202, the secure element 428 may be conventional in its hardwareaspects. In some embodiments, functionality as described below may beprogrammed into the secure element and/or other processing elements inthe mobile device 202 in accordance with aspects of the presentdisclosure. (It should be noted that the term “secure element” is notintended to be limited to devices that are IC-based, but rather, mayalso include any secure execution environment in a mobile device, andmay include software based secure execution environments running on themain mobile device processor.) In some embodiments, the secure element428 may be provisioned or pre-programmed with one or more paymentapplication programs (“apps”) such that the mobile device is enabled tooperate as a payment device vis-à-vis POS terminals (assuming that themobile device is also provisioned with payment account credentialsdata).

For the purpose of conducting payment account transactions, the mobiledevice 202 may communicate with POS terminals via the antenna 426 inaccordance with the NFC communication standard. Further, according toaspects of the present disclosure, the secure element 428 or otherprogrammable component(s) of the mobile device 202 may be programmedsuch that the mobile device 202 is enabled to interact with anauthentication device, such as that described herein and in a mannerdescribed below in connection with FIGS. 6A and 6B. For this purpose,for example, a user/device authentication app may be installed in themobile device 202 to enable the authentication functionality describedherein.

As will be understood from subsequent discussion, authentication of theuser of the mobile device 202 may include gathering of biometricinformation from the user by the mobile device. Fingerprint scanning,facial recognition processing and/or voice recognition processing areamong the possible modes of biometric authentication of the user. Block430 in FIG. 4 represents one or more hardware and/or software featuresof the mobile device 202 that enable biometric data input to the mobiledevice. The biometric input unit 430 may be stand-alone relative toother hardware features of the mobile device 202 or may be incorporatedin or overlap with other hardware features. For example, the touchscreen412 may incorporate a fingerprint scanning function; the microphone 420may serve as an input for voice utterances of the user to be employedfor voice recognition; and/or the camera (not shown apart from block430) may be employed to capture an image of the user's face or retinafor facial/retina recognition purposes. Other types of biometric userauthentication may also or alternatively be employed, including gaitrecognition, electronic keypad interaction pattern recognition, and/orother types of biometric measures previously proposed or proposedsubsequent to the time of this disclosure.

It should also be understood that the mobile device 202 may be operableas a conventional mobile telephone for communication—both voice anddata—over a conventional mobile telecommunications network, which is notdepicted in the drawing apart from element 208 in FIG. 2. Thus, themobile device 102 may be in communication from time to time in aconventional manner with a mobile network operator (“MNO”—not shown).

As is familiar to those who are skilled in the art, the mobile device202 may be viewed as a small computing device. The mobile device 202 mayinclude one or more processors that are programmed by software, appsand/or other processor-executable steps to provide functionality asdescribed herein. The software, apps and/or other processor-executablesteps may be stored in one or more computer-readable storage media (suchas the storage devices 406 and/or the secure element 428) and maycomprise program instructions, which may be referred to as computerreadable program code means. Through its computing and datacommunication capabilities, the mobile device 202 may have capabilitiesfor engaging in remote communications with the credentials back-upcomputer 206.

FIG. 5 is a block diagram that illustrates an example embodiment of thepayment credentials back-up computer 206 shown in FIG. 2. Thecredentials back-up computer 206 may also sometimes be referred to as a“back-up services computer.”

The credentials back-up computer 206 may be constituted by standardcomponents in terms of its hardware and architecture, but may becontrolled by software to cause it to function as described herein. Forexample, the credentials back-up computer 206 may be constituted byserver computer hardware.

The credentials back-up computer 206 may include a computer processor500 operatively coupled to a communication device 501, a storage device504, an input device 506 and an output device 508.

The computer processor 500 may be constituted by one or more processors.Processor 500 operates to execute processor-executable steps, containedin program instructions described below, so as to control thecredentials back-up computer 206 to provide desired functionality.

Communication device 501 may be used to facilitate communication with,for example, other devices (such as numerous mobile devices seekingcredentials data loading services and/or other devices that submitcredentials data for storage in the credentials back-up computer 206 ina user's partition maintained in the credentials back-up computer 206).For example (and continuing to refer to FIG. 5), communication device501 may comprise numerous communication ports (not separately shown), toallow the credentials back-up computer 206 to communicate simultaneouslywith a number of other computers and other devices.

Input device 506 may comprise one or more of any type of peripheraldevice typically used to input data into a computer. For example, theinput device 506 may include a keyboard and a mouse. Output device 508may comprise, for example, a display and/or a printer.

Storage device 504 may comprise any appropriate information storagedevice, including combinations of magnetic storage devices (e.g., harddisk drives), optical storage devices such as CDs and/or DVDs, and/orsemiconductor memory devices such as Random Access Memory (RAM) devicesand Read Only Memory (ROM) devices, as well as so-called flash memory.Any one or more of such information storage devices may be considered tobe a computer-readable storage medium or a computer usable medium or amemory.

Storage device 504 stores one or more programs for controlling processor500. The programs comprise program instructions (which may be referredto as computer readable program code means) that containprocessor-executable process steps of the credentials back-up computer206, executed by the processor 500 to cause the credentials back-upcomputer 206 to function as described herein.

The programs may include one or more conventional operating systems (notshown) that control the processor 500 so as to manage and coordinateactivities and sharing of resources in the credentials back-up computer206, and to serve as a host for application programs (described below)that run on the credentials back-up computer 206.

The storage device 504 may store a credentials data vault management andmaintenance program 510 that controls the processor 500 to enable thecredentials back-up computer 206 to act as a credentials data repositoryfor a large base of users/subscribers. In some embodiments, the program510 may allow users to enroll and establish dedicated data partitionsfor themselves in the credentials back-up computer 206. The program 510may also operate to receive and store in each user's partitionrespective credentials data. In some embodiments, the stored credentialsdata may include payment credentials relating to one or more paymentaccounts for a given user. In some embodiments, the payment credentialsstored for a given user may include credentials relating to two, threeor more payment accounts of different types and/or from differentaccount issuers. The different types of payment accounts may includecredit, debit, prepaid, or other types of accounts typically used fortransactions involving payment networks. In some embodiments, thecredentials for a given account may include, e.g., an account number orsubstitute (payment token), expiration date, security code (e.g., CVC),account holder's name, etc. In some embodiments, the account issuers mayinclude a number of different financial institutions. In someembodiments, the credentials may include data that supportsfunctionality in addition to or instead of payment transactions. Forexample, such functionality may include transit system access; building,facility or room access; customer loyalty account identifiers; proof ofmembership (e.g., to a health club or other private facility); proof ofidentity—including, for example, a driver's license, a passport, voterregistration, or a digitized version of any other kind of identity card.

Continuing to refer to FIG. 5, the programs stored in the storage device504 may also include an access request handling application program 512that controls the processor 500 to enable the credentials back-upcomputer 206 to handle requests for access to the back-up credentialsdata stored in the credentials back-up computer 206. The manner in whichsuch requests may occur and may be handled will be described below,particularly with reference to FIGS. 6A and 6B.

The storage device 504 may also store, and the credentials back-upcomputer 206 may also execute, other programs, which are not shown. Forexample, such programs may include a reporting application, which mayrespond to requests from system administrators for reports on theactivities performed by the credentials back-up computer 206. The otherprograms may also include, e.g., one or more data communicationprograms, database management programs, device drivers, etc.

The storage device 504 may also store one or more databases 514 requiredfor operation of the credentials back-up computer 206. For example, theback-up credentials data referred to above may be stored as one or moreof the databases 514.

FIGS. 6A and 6B together form a flow chart that illustrates a processthat may be performed in the system 200 shown in FIG. 2, in accordancewith aspects of the present disclosure.

At 602, credentials data is stored in the credentials back-up computer206 for a particular user. This may occur in a number of ways. Forexample, the user of a mobile device (not shown, and assumed not to bethe mobile device 202 shown in FIG. 2) that has been loaded withcredential data may access a website hosted by the credentials back-upcomputer 206. The user may operate the mobile device to establish anaccount as a subscriber to the credentials data back-up service providedthrough the credentials back-up computer 206. As part of the sameprocess, the user may operate the mobile device to upload thecredentials data that has been stored therein. The credentials data may,for example, include some or all of the types of data enumerated abovein connection with the description of the back-up vault managementsoftware application 510 shown in FIG. 6A. To reiterate just one exampleof such data, the credentials data uploaded from the mobile device mayinclude payment credentials for a number of different payment accountsthat are accessible via a wallet application that runs on the mobiledevice. In some embodiments, the mobile device may also upload biometricdata related to the user. This biometric data may serve as referencedata for a subsequent user authentication process to be described below.In addition or alternatively, the mobile device may upload a PIN,selected by the user, to be utilized for subsequent user authentication.

Alternatively, one or more account issuers or wallet service providersthat have a relationship with the user may facilitate the user'ssubscription to the back-up service and/or may transfer credentials datafor the user to be stored in the user's partition in the credentialsback-up computer 206. Other issuers of digitized or digitizablecredentials may similarly transfer credentials data for the user to thecredentials back-up computer 206.

In connection with the user's opening of a subscriber account with thecredentials back-up computer 206 and/or in connection with storage ofthe user's credentials data in the credentials back-up computer 206, theoperator of the credentials back-up computer 206 may issue to the userthe above-mentioned authentication device 204 (FIGS. 2 and 3). In someembodiments, for example, the authentication device 204 may be sent tothe user by postal mail. It may be the case that the mailing package forthe authentication device 204 may suggest to the user that he/she shouldkeep the authentication device 204 in a secure location in his/herresidence, and not carry the authentication device 204 on his/herperson. The mailing package may also contain instructions as to how theuser can access the back-up credentials data using the authenticationdevice 204. In some embodiments, the authentication device 204, asissued by the operator of the credentials back-up computer 206, maystore user authentication reference data, such as a PIN or biometricreference data for the user. That is, the credentials back-up computer206 may, as part of issuance of the authentication device 204, load intothe authentication device 204 user authentication reference datapreviously uploaded to, or generated by, the credentials back-upcomputer 206.

In some embodiments, the authentication device 204 may be issued to theuser by an issuer of one or more of the user's payment accounts. Indoing so, the account issuer may be operating in cooperation with and inplace of the operator of the credentials back-up computer 206. In someembodiments, the operator of the credentials back-up computer 206 may bean account issuer and/or a financial institution. In such a case, theback-up credentials service may be offered by the account issuer as asupplement to payment account services and/or other services that theaccount issuer provides to the user.

It will now be assumed that, after a lapse of time following the storageof the user's credentials data in the credentials back-up computer 206and issuance of the authentication device 204, the user needs or wantsto replace his/her mobile device. It is also assumed that the user hasbeen using the to-be-replaced device to access various credentials,including, for example, payment account credentials used for paymentaccount transactions. A further assumption is that the user has obtainedthe replacement mobile device, which is indicated by reference numeral202 in FIG. 2. Accordingly, the user may initiate a process of accessinghis/her stored back-up credentials via his/her new mobile device 202.This may involve the user interacting with an app on the mobile device202 such that the mobile device enters into communications (block 604,FIG. 6A) with the credentials back-up computer 206. (In someembodiments, the commencement of communications between the mobiledevice 202 and the credentials back-up computer 206 may be delayed to alater stage of the process of FIG. 6A/6B.)

At 606 in FIG. 6A, the user may bring the authentication device 204 intoproximity with the mobile device 202. The mobile device 202 mayinterrogate the authentication device 204, bringing about short-rangewireless data communications between the two devices, as indicated at210 in FIG. 2, and by block 608 in FIG. 6A. In some embodiments, thecommunication between the mobile device 202 and the authenticationdevice 204 may be in accordance with the NFC (near field communication)standard.

The mobile device 202 may then prompt the user to provide input toauthenticate himself/herself. In some embodiments, this may include theuser entering a PIN (personal identification number) into the mobiledevice 202. In addition or alternatively, the user may provide his/herthumb/finger for fingerprint scanning by the mobile device 202. Othertypes of biometric input are also or alternatively possible, as referredto above. The input of the user authentication data by the user into themobile device 202 is represented by block 610 in FIG. 6A.

At block 612 in FIG. 6A, the mobile device 202 transmits the userauthentication data to the authentication device 204. At block 614, theauthentication device 204 receives the user authentication data from themobile device 202.

At block 616, the authentication device 204 performs a verificationprocess with respect to the user authentication data. That is, theauthentication device 204 verifies the user authentication data. In acase where the authentication data is a PIN entered into the mobiledevice 202 by the user, the verification process may involve theauthentication device 204 determining whether the authentication datamatches reference PIN data that was stored in the authentication device204 at the time the authentication device 204 was issued. In a casewhere the authentication data is derived from a biometric measureperformed by the mobile device 202, the verification process may involvethe authentication device 204 determining whether the authenticationdata matches reference biometric data that was previously obtained froma like biometric measure with respect to the user and stored in theauthentication device 204 at the time the authentication device 204 wasissued.

A decision block 618 may follow block 616 in the process of FIG. 6A. Atdecision block 618, the authentication device 204 may determine whetherthe verification process of block 616 was performed successfully. If so,then block 620 may follow decision block 618. That is, execution ofblock 620 may depend on a result of the verification process.

At block 620, the authentication device 204 may generate a cryptogram,as is known in the relevant art. For example, the authentication device204 may employ a public cryptographic key stored in the authenticationdevice 204 to digitally sign an unpredictable challenge valuetransmitted to the authentication device 204 from the mobile device 202.The unpredictable challenge value may have been generated by a random orpseudo-random process in the mobile device 202 in connection with theuser authentication process and transmitted along with (or shortlybefore or after) transmission of the authentication data from the mobiledevice 202 to the authentication device 204. The digitally signedunpredictable value is one type of cryptogram that the authenticationdevice 204 may generate in some embodiments of block 620. In otherembodiments, the authentication device 204 may perform other types ofcryptographic processes to generate the cryptogram.

Referring again to decision block 618, if a negative determination ismade at that decision block (i.e., if the authentication device 204determines that the verification process was not successful), then block622 may follow decision block 618. At block 622, the authenticationdevice 204 may prompt the mobile device 202 to display an appropriateerror message to the user, and the process of FIGS. 6A/6B may then end.

Considering again block 620 in FIG. 6A, block 624 may follow block 620.At block 624, the authentication device may transmit, to the mobiledevice 202, the cryptogram generated by the authentication device 204 atblock 620.

At block 626 in FIG. 6B, the mobile device 202 may receive thecryptogram transmitted by the authentication device 204 at 624.

Continuing to refer to FIG. 6B, at block 628 the mobile device 202 maytransmit the cryptogram to the credentials back-up computer 206. At thesame time, the mobile device 202 may transmit, to the credentialsback-up computer 206, data provided from the mobile device 202 that wasused by the authentication device 204 to generate the cryptogram.

At block 630, the credentials back-up computer 206 may receive thecryptogram transmitted from the mobile device 202 at 628. At block 632,the credentials back-up computer 206 may perform a verification processwith respect to the cryptogram it received at 630. That is, thecredentials back-up computer 206 verifies the cryptogram. For example,where the cryptogram was generated by the authentication device 204 byusing a public key, the credentials back-up computer 206 may decrypt thecryptogram using the corresponding private key. The credentials back-upcomputer 206 may then determine whether the decrypted result matches anexpected value (e.g., an unpredictable value produced by the mobiledevice 202 and supplied to both the authentication device 204 and thecredentials back-up computer 206).

A decision block 634 may follow block 632 in the process of FIG. 6B. Atdecision block 634, the credentials back-up computer 206 may determinewhether the verification process of block 632 was performedsuccessfully. If so, then block 636 may follow decision block 634. Thatis, execution of block 636 may depend on a result of the verificationprocess of block 632.

At block 636, the credentials back-up computer 206 may make the back-upcredentials data available to the mobile device 202. For example, thismay include downloading all of the back-up credentials data for the userto the mobile device 202. For example, the back-up credentials data maybe downloaded for storage in the SE 428 (FIG. 4) in the mobile device202. In other embodiments, some or all of the back-up credentials datamay be provided to a server computer (not shown) that serves as a remotehost for credentials data to be accessed via a secure executionenvironment (SEE) on the mobile device 202. In some embodiments, thecredentials back-up computer 206 itself, or an associated computersystem, may serve as the remote host for credentials data for the SEE onthe mobile device 202.

In conjunction with making the back-up credentials data accessible tothe mobile device 202, the credentials back-up computer 206 may takeappropriate steps to block any other or previous mobile device (notshown) from using/accessing the credentials data that was previouslyaccessible to the previous mobile device. For example, the credentialsback-up computer 206 may perform a “remote wipe” operation on theprevious mobile device, at least with respect to the relevantcredentials data. In addition or alternatively, the credentials back-upcomputer 206 may provide notice to account issuers and/or other issuersof the credentials that the old mobile device has been replaced by themobile device 202 in terms of accessing the credentials.

Referring again to decision block 634 in FIG. 6B, if a negativedetermination is made at decision block 634 (i.e., if the credentialsback-up computer 206 determines that the verification process of block632 was not successful), then block 638 may follow decision block 634.At block 638, the credentials back-up computer 206 may prompt the mobiledevice 202 to display an appropriate error message to the user, and theprocess may end. It will be recognized that in this case the mobiledevice may not be permitted access to the back-up credentials data forthe user, or may be required to retry the process.

With a process as described above, and particularly with anauthentication device such as that described herein, shiftingcredentials data from an old (or lost or stolen) mobile device to a newmobile device may be accomplished with a high degree of convenience forthe user, and also with a high degree of security for preventingunauthorized access to the credentials data. Because of the securityafforded by the authentication device, it may be feasible to omit ID&V(identification and verification) processes that account issuers mightotherwise require for provisioning existing payment accounts to a newmobile device.

In embodiments described above, the authentication device 204 wasillustrated as being card-shaped (e.g., akin to a conventional paymentcard in shape and size). Alternatively, however, the authenticationdevice may be provided in other form factors, such as fobs, wristbands,etc.

In addition to or instead of providing back-up services with respect tocredentials data, the credentials back-up computer 206 may providesimilar services with respect to contact lists, appointment data, textmessage threads, photographs and any other personal data typicallystored by users on their mobile devices. To support such functionality,mobile devices may periodically “sync up” with the credentials back-upcomputer 206 to update the back-up data to be transferred upon theuser's adoption of a new mobile device.

In embodiments described above, the credentials back-up computer 206 hasbeen portrayed as a centralized computer resource serving many mobiledevice users. However, in other embodiments, the back-up function may belocally implemented on, e.g., a personal computer/server that the mobiledevice user owns and controls, and has located in his/her residence.

As used herein and in the appended claims, the term “computer” should beunderstood to encompass a single computer or two or more computers incommunication with each other.

As used herein and in the appended claims, the term “processor” shouldbe understood to encompass a single processor or two or more processorsin communication with each other.

As used herein and in the appended claims, the term “memory” should beunderstood to encompass a single memory or storage device or two or morememories or storage devices.

The flow charts and descriptions thereof herein should not be understoodto prescribe a fixed order of performing the method steps describedtherein. Rather the method steps may be performed in any order that ispracticable.

As used herein and in the appended claims, the term “payment account”includes a credit card account, a deposit account that the accountholder may access using a debit card, a prepaid card account, or anyother type of account from which payment transactions may beconsummated. The terms “payment account,” “payment card system account”and “payment card account” are used interchangeably herein. The term“payment card account number” includes a number that identifies apayment card system account or a number carried by a payment card, or anumber that is used to route a transaction in a payment system thathandles debit card and/or credit card transactions. The term “paymentcard” includes a credit card, debit card, prepaid card, or other type ofpayment instrument, whether an actual physical card or virtual.

As used herein and in the appended claims, the term “payment system”refers to a system for handling purchase transactions and relatedtransactions. An example of such a system is the one operated byMasterCard International Incorporated, the assignee of the presentdisclosure. In some embodiments, the term “payment system” may belimited to systems in which member financial institutions issue paymentaccounts to individuals, businesses and/or other organizations.

Although the present disclosure has been described in connection withspecific exemplary embodiments, it should be understood that variouschanges, substitutions, and alterations apparent to those skilled in theart can be made to the disclosed embodiments without departing from thespirit and scope of the disclosure as set forth in the appended claims.

What is claimed is:
 1. An authentication device, comprising: aprocessor; a memory in communication with the processor; and ashort-range data communication transceiver controlled by the processor;the memory storing program instructions, the processor operative withthe program instructions to perform functions as follows: receiving userauthentication data via the transceiver from a mobile device inproximity to the authentication device; verifying the received userauthentication data; receiving challenge data from the mobile device; inresponse to a result of the verifying function, generating a cryptogramby digitally signing the challenge data with a cryptographic key; andtransmitting the cryptogram via the transceiver to the mobile device;said challenge data randomly or pseudo-randomly generated by the mobiledevice.
 2. The authentication device of claim 1, wherein the receiveduser authentication data includes a PIN (personal identificationnumber).
 3. The authentication device of claim 1, wherein the receiveduser authentication data includes user biometric data.
 4. Theauthentication device of claim 3, wherein the user biometric datarepresents a scan of the user's fingerprint.
 5. The authenticationdevice of claim 3, wherein the user biometric data is suitable for voicerecognition processing.
 6. The authentication device of claim 1, whereinthe authentication device is card-shaped.
 7. The authentication deviceof claim 1, wherein the mobile device is a smartphone.
 8. A method ofauthenticating a user of a mobile device, the method comprising:operating the mobile device, the mobile device including a mobiletelecommunications transceiver and a short-range data communicationstransceiver; establishing a communication channel via the mobiletelecommunications transceiver with a back-up service computer;exchanging short-range wireless data communications with anauthentication device via the short-range data communicationtransceiver, the authentication device different from the mobile device;receiving user authentication data in the mobile device; transmittingthe user authentication data to the authentication device via theshort-range data communication transceiver; receiving a cryptogram fromthe authentication device via the short-range data communicationtransceiver; and transmitting the received cryptogram to the back-upservice computer via the mobile telecommunications transceiver.
 9. Themethod of claim 8, further comprising: generating challenge data; andtransmitting the challenge data to the authentication device.
 10. Themethod of claim 9, further comprising: receiving a download of back-upcredentials data from the back-up service computer after said step oftransmitting the cryptogram.
 11. The method of claim 10, wherein thedownloaded back-up credentials data includes payment accountcredentials.
 12. The method of claim 11, wherein the payment accountcredentials include at least one of: (a) a PAN (primary account number);and (b) a payment token.
 13. The method of claim 11, wherein the paymentaccount credentials include credentials for a plurality of paymentaccounts.
 14. The method of claim 13, wherein the plurality of paymentaccounts include a first payment account issued by a first accountissuer and a second payment account issued by a second account issuerdifferent from the first account issuer.
 15. The method of claim 8,wherein the user authentication data includes a PIN (personalidentification number).
 16. The method of claim 8, wherein the userauthentication data includes user biometric data.
 17. The method ofclaim 16, wherein the user biometric data represents a scan of theuser's fingerprint.
 18. An apparatus for confirming authentication of auser of a mobile device, the apparatus comprising: a processor; and amemory in communication with the processor, the memory storing programinstructions, the processor operative with the program instructions toperform functions as follows: storing back-up credentials data for auser; establishing a communications channel with the mobile device;receiving a cryptogram and challenge data from the mobile device, thecryptogram relayed by the mobile device from an authentication devicethat interacted with the mobile device to support authentication of auser of the mobile device and the authentication device, theauthentication device different from the mobile device, theauthentication device associated with the user; verifying the cryptogramby using the challenge data to verify data obtained by decrypting thecryptogram; and in response to a result of the step of verifying thecryptogram, making the stored back-up credentials data accessible to themobile device.
 19. The apparatus of claim 18, wherein the communicationschannel is at least partially constituted by a mobile communicationsnetwork.
 20. The apparatus of claim 18, wherein the stored back-upcredentials data is made accessible to the mobile device by downloadingthe stored back-up credentials data to the mobile device.